The intent of the safety requirements specification is to identify each software based function whose failure could
lead to a violation of technical safety requirement that has been allocated to software. This is derived from the
technical safety concept and the systems design and shall consider.
The specified system and hw configurations
The hardware software interface specification
The relevant requirements of the HW design specification
Timing constraints
External interfaces
Each operating mode of the vehicle, the system, or the
hardware, having an impact on the software.
If ASIL decomposition is applied to the software safety
requirements, ISO 26262-vol 9, Clause 5, shall be complied with.
If there are other functions (not related to the safety requirements) that are to be carried out by the same piece of
embedded software, these functions shall also be specified or a reference made to the specification.
Within the software safety requirements there should be enough information to allow the SW design and related
development, verification, validation and functional safety assessment activities to be carried out effectively.
For more details the user is referred to ISO 26262, vol 6, clauses 6.4.1, 3 and 5.
The software safety specification can be derived (if employing a use case based approach) using Build and Validate Use Cases [Scenario Driven] if the focus of the use
cases is safety based. From this the HW/SW interfaces can also be derived.
|